home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: FW_DECLARE_AUTO
- Sent: 5/22/96 10:28 AM
- Received: 5/22/96 10:51 AM
- From: Henri Lamiraux, lamiraux@apple.com
- Reply-To: ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- >Dear ODF Team:
- >
- >Should all classes that use the FW_DECLARE_AUTO macro also use the
- >FW_END_CONSTRUCTOR and FW_START_DESTRUCTOR macros and vice-versa?
- >
- >I ask the question because this rule is not always true with ODF example
- >code. Among other, CHelloDragCommand uses the FW_DECLARE_AUTO macro, but
- >its destructor has no FW_START_DESTRUCTOR macro. The CNothingPart also uses
- >the FW_DECLARE_AUTO macro, but neither its constructor nor its destructor
- >uses the FW_END_CONSTRUCTOR and FW_START_DESTRUCTOR macros.
- >
- >What is really strange is that not using the proper macro combination
- >causes link errors with my part, but it is obviously not always the case
- >since you did compile ODF examples...
- >
- >Serge
- >
-
-
- Yes, if you use the FW_DECLARE_AUTO macro you need to use the
- FW_START_DESTRUCTOR and
- FW_END_CONSTRUCTOR macros.
-
- If you use the CodeWarrior native exceptions you don't need to use at all
- those macros.
-
- .......................................................................
- Henri Lamiraux lamiraux@apple.com
- Apple Computer, Inc. OpenDoc(tm) Development Framework
- .......................................................................
-
-